Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shrink unsafe block #244

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Shrink unsafe block #244

wants to merge 1 commit into from

Conversation

cactter
Copy link

@cactter cactter commented Jul 21, 2022

In this function you use the unsafe keyword for almost the entrie function body.

We need to mark unsafe operations more precisely using unsafe keyword. Keeping unsafe blocks small can bring many benefits. For example, when mistakes happen, we can locate any errors related to memory safety within an unsafe block. This is the balance between Safe and Unsafe Rust. The separation is designed to make using Safe Rust as ergonomic as possible, but requires extra effort and care when writing Unsafe Rust.

Hope this PR can help you.
Best regards.
References
https://doc.rust-lang.org/nomicon/safe-unsafe-meaning.html
https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html

@PureTryOut
Copy link
Collaborator

Thanks @cactter! However seems CI fails on the formatting check. Could you fix it?

@terrarier2111
Copy link
Member

Thanks @cactter! However seems CI fails on the formatting check. Could you fix it?

I am currently rewriting our entire rendering code to use wgpu-mc, so i don't think this is worth while as all unsafe code which was shrunk is part of said rendering part

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants